Desktop error repair tool

ABSTRACT

An apparatus includes a scanner and a resolution engine. The scanner detects first and second software exceptions. The scanner also determines that the first software exception occurred previously in a plurality of desktops and that the second software exception did not occur previously in the plurality of desktops. The resolution engine determines a first solution and a second solution for resolving the first software exception and that the first solution has a higher ranking than the second solution. The resolution engine also generates a software patch that implements the first solution and deploys the software patch. The resolution engine further determines a series of steps implemented to resolve the second software exception and records the series of steps to prepare a second software patch if the second software exception occurs again in the plurality of desktops.

TECHNICAL FIELD

This disclosure relates generally to repairing software errors incomputers.

BACKGROUND

Computers are used ubiquitously throughout organizations by members andemployees. The computers may execute applications that perform variousfunctions.

SUMMARY OF THE DISCLOSURE

According to an embodiment, an apparatus includes a scanner and aresolution engine. The scanner detects, in a desktop of a plurality ofdesktops, a first software exception occurring in an application of aplurality of executing applications and detects, in a desktop of theplurality of desktops, a second software exception occurring in anapplication of the plurality of executing applications. The scanner alsodetermines that the first software exception occurred previously in theplurality of desktops and determines that the second software exceptiondid not occur previously in the plurality of desktops. The resolutionengine determines a first solution and a second solution for resolvingthe first software exception and determines that the first solution hasa higher ranking than the second solution. The resolution engine alsogenerates a software patch that implements the first solution inresponse to the determination that the first solution has a higherranking than the second solution and deploys the software patch. Theresolution engine further determines a series of steps implemented toresolve the second software exception and records the series of steps toprepare a second software patch if the second software exception occursagain in the plurality of desktops.

According to another embodiment, a method includes detecting, in adesktop of a plurality of desktops, a first software exception occurringin an application of a plurality of executing applications anddetecting, in a desktop of the plurality of desktops, a second softwareexception occurring in an application of the plurality of executingapplications. The method also includes determining that the firstsoftware exception occurred previously in the plurality of desktops anddetermining that the second software exception did not occur previouslyin the plurality of desktops. The method further includes determining afirst solution and a second solution for resolving the first softwareexception and determining that the first solution has a higher rankingthan the second solution. The method also includes generating a softwarepatch that implements the first solution in response to thedetermination that the first solution has a higher ranking than thesecond solution and deploying the software patch. The method furtherincludes determining a series of steps implemented to resolve the secondsoftware exception and recording the series of steps to prepare a secondsoftware patch if the second software exception occurs again in theplurality of desktops.

According to yet another embodiment, a system includes a plurality ofdesktops and a desktop repair tool. The desktop repair tool detects, ina desktop of the plurality of desktops, a first software exceptionoccurring in an application of a plurality of executing applications anddetects, in a desktop of the plurality of desktops, a second softwareexception occurring in an application of the plurality of executingapplications. The desktop repair tool also determines that the firstsoftware exception occurred previously in the plurality of desktops anddetermines that the second software exception did not occur previouslyin the plurality of desktops. The desktop repair tool further determinesa first solution and a second solution for resolving the first softwareexception and determines that the first solution has a higher rankingthan the second solution. The desktop repair tool also generates asoftware patch that implements the first solution in response to thedetermination that the first solution has a higher ranking than thesecond solution and deploys the software patch. The desktop repair toolfurther determines a series of steps implemented to resolve the secondsoftware exception and records the series of steps to prepare a secondsoftware patch if the second software exception occurs again in theplurality of desktops.

Certain embodiments provide one or more technical advantages. Forexample, an embodiment repairs software exceptions occurring indesktops. As another example, an embodiment generates software patchesto repair desktops. Certain embodiments may include none, some, or allof the above technical advantages. One or more other technicaladvantages may be readily apparent to one skilled in the art from thefigures, descriptions, and claims included herein.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, referenceis now made to the following description, taken in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates a computer system;

FIG. 2 illustrates a desktop repair tool of the system of FIG. 1; and

FIG. 3 is a flowchart illustrating a method for repairing desktops usingthe system of FIG. 1.

DETAILED DESCRIPTION

Embodiments of the present disclosure and its advantages are bestunderstood by referring to FIGS. 1 through 3 of the drawings, likenumerals being used for like and corresponding parts of the variousdrawings.

Computers are used ubiquitously throughout organizations by members andemployees. The computers may execute applications that perform variousfunctions required by the operating member or employee. Some computersmay execute the same applications if the members or employees performthe same function. Some computers may execute different applications ifthe members or employees perform different functions within theorganization. As an organization grows, so does the number of computersand applications within that organization.

In certain instances, applications may contain bugs that cause errorsand/or failures. However, these bugs may only be triggered by specificworkflows such that the occurrences of errors and/or failures caused bythe bugs may be sporadic or unpredictable. Additionally, an organizationmay be dispersed across different geographies and/or locations. When abug causes an error or failure, the application and/or computer may berepaired by someone who is local to that computer or application. Ifthat error or failure occurs in different locations of the organization,then different people may be tasked with repairing the error or failure.These repairmen may not have the same knowledge base and may not attemptto repair the error or failure in the same manner. Some may be able torepair the error or failure and some may not. Additionally, some mayrepair the error or failure without actually addressing the underlyingbug. As a result, computers across the organization may remainunrepaired and software bugs may remain untreated.

This disclosure contemplates an unconventional desktop repair tool thatdetects software exceptions and determines resolutions for theexceptions. The desktop repair tool learns the proper steps forrepairing software exceptions and implements those steps and/orresolutions across an organization. In certain embodiments, the desktoprepair tool improves the process for repairing a desktop and/or softwareapplication by implementing solutions and/or patches for those desktopsand/or applications. By using the desktop repair tool, desktops acrossan organization may have their software bugs, errors, and/or failuresrepaired in a timely and consistent manner. The desktop repair tool willbe described generally using FIG. 1. FIGS. 2 and 3 will describe thedesktop repair tool in more detail.

FIG. 1 illustrates a computer system 100. As illustrated in FIG. 1,system 100 includes one or more devices 110, a network 115, a database120, and a desktop repair tool 125. In particular embodiments, system100 improves the functioning of devices 110 by repairing bugs, errors,and/or failures that occur in devices 110.

Devices 110 may be used by users 105 to perform various functions. Eachdevice 110 may execute an application 130 or multiple applications 130to perform these tasks. Devices 110 may execute different applications130 depending on the desires and expectations of a user 105 of aparticular device 110. As the number of user 105 and devices 110 grows,so does the number of applications 130 being executed in system 100.

In some instances, a particular application 130 may not have beendeveloped perfectly. In other words, the application 130 may includebugs that cause errors and/or failures. In some instances, these bugsmay only be triggered when a user 105 performs a certain workflow inapplication 130. In other words, even though two users 105 are using thesame application 130, it may not be the case that both users 105 willencounter the same bug in all instances. It may even be the case thatboth users 105 may not encounter the bug at all.

When a bug is triggered and an error or failure results, it may benecessary to repair the application 130 and/or device 110. A localrepair person may attempt to correct the error and/or failure and torepair the bug. However, that repair person may not have a sufficientknowledge base to repair the bug. In these instances, the bug may gounrepaired and the device 110 and/or application 130 may fail in thefuture because of the same bug.

Devices 110 may be any appropriate device for communicating withcomponents of system 100 over network 115. For example, devices 110 maybe a telephone, a mobile phone, a computer, a laptop, a tablet and/or anautomated assistant. This disclosure contemplates device 110 being anyappropriate device for sending and receiving communications over network115. As an example and not by way of limitation, device 110 may be acomputer, a laptop, a wireless or cellular telephone, an electronicnotebook, a personal digital assistant, a tablet, or any other devicecapable of receiving, processing, storing, and/or communicatinginformation with other components of system 100. Device 110 may alsoinclude a user interface, such as a display, a microphone, keypad, orother appropriate terminal equipment usable by user 105. In someembodiments, an application executed by device 110 may perform thefunctions described herein.

Network 115 facilitates communication between and amongst the variouscomponents of system 100. This disclosure contemplates network 115 beingany suitable network operable to facilitate communication between thecomponents of system 100. Network 115 may include any interconnectingsystem capable of transmitting audio, video, signals, data, messages, orany combination of the preceding. Network 115 may include all or aportion of a public switched telephone network (PSTN), a public orprivate data network, a local area network (LAN), a metropolitan areanetwork (MAN), a wide area network (WAN), a local, regional, or globalcommunication or computer network, such as the Internet, a wireline orwireless network, an enterprise intranet, or any other suitablecommunication link, including combinations thereof, operable tofacilitate communication between the components.

Database 120 stores information used by other components of system 100.For example, database 120 may store various resolutions for bugs thatoccur in application 130. Database 120 may retrieve and send any storedinformation to other components of system 100. For example, database 120may retrieve and send resolutions and other information about bugs,errors, and/or failures to other components.

Desktop repair tool 125 provides resolutions for bugs, errors, and/orfailures in devices 110. As illustrated in FIG. 1, desktop repair tool125 includes a processor 135 and a memory 140. This disclosurecontemplates processor 135 and memory 140 being configured to performany of the functions of desktop repair tool 125 described herein. Inparticular embodiments, desktop repair tool 125 improves the functioningof devices 110 by resolving bugs, errors and/or failures in devices 110.

Processor 135 is any electronic circuitry, including, but not limited tomicroprocessors, application specific integrated circuits (ASIC),application specific instruction set processor (ASIP), and/or statemachines, that communicatively couples to memory 140 and controls theoperation of desktop repair tool 125. Processor 135 may be 8-bit,16-bit, 32-bit, 64-bit or of any other suitable architecture. Processor135 may include an arithmetic logic unit (ALU) for performing arithmeticand logic operations, processor registers that supply operands to theALU and store the results of ALU operations, and a control unit thatfetches instructions from memory and executes them by directing thecoordinated operations of the ALU, registers and other components.Processor 135 may include other hardware and software that operates tocontrol and process information. Processor 135 executes software storedon memory to perform any of the functions described herein. Processor135 controls the operation and administration of desktop repair tool 125by processing information received from network 115, device(s) 110, andmemory 140. Processor 135 may be a programmable logic device, amicrocontroller, a microprocessor, any suitable processing device, orany suitable combination of the preceding. Processor 135 is not limitedto a single processing device and may encompass multiple processingdevices.

Memory 140 may store, either permanently or temporarily, data,operational software, or other information for processor 135. Memory 140may include any one or a combination of volatile or non-volatile localor remote devices suitable for storing information. For example, memory140 may include random access memory (RAM), read only memory (ROM),magnetic storage devices, optical storage devices, or any other suitableinformation storage device or a combination of these devices. Thesoftware represents any suitable set of instructions, logic, or codeembodied in a computer-readable storage medium. For example, thesoftware may be embodied in memory 140, a disk, a CD, or a flash drive.In particular embodiments, the software may include an applicationexecutable by processor 135 to perform one or more of the functionsdescribed herein.

Desktop repair tool 125 detects exceptions 145A and 145B in devices 110and/or applications 130. When a bug causes an error and/or failure inapplication 130, the application 130 may throw an exception 145. Theexception may indicate the type of failure and/or the symptoms of thefailure. The exception 145 may not indicate the underlying cause of thefailure. The exception 145 may also not indicate the bug that caused theerror and/or failure.

An exception 145 may occur in a particular application 130 executing ona particular device 110 of system 100. Different devices 110 and/ordifferent applications 130 may throw different exceptions 145. Forexample, exception 145A may have been thrown by a first application 130in a first device 110 of system 100. Exception 145B may have been thrownby a different application 130 executing in a different device 110 ofsystem 100. Exception 145A and exception 145B may indicate differentfailures that occurred in different applications 130. In some instances,exception 145A and exception 145B may have been thrown by the sameapplication 130 executing on different devices 110 or by differentapplications 130 executing on the same device 110.

Desktop repair tool 125 may monitor devices 110 and/or applications 130in system 100 to detect when exceptions 145 have been thrown by anapplication 130. When desktop repair tool 125 detects that an exception145 has been thrown, desktop repair tool 125 may endeavor to resolve theexception 145.

Desktop repair tool 125 may first determine whether an exception 145 hasoccurred previously in system 100 such as, for example, in anotherdevice 110 of system 100. Desktop repair tool 125 may search database120 for a detected exception 145. For example, desktop repair tool 125may search database 120 using keywords indicated by exception 145. Asearch of database 120 may reveal whether the particular exception 145has occurred previously and the various resolutions for that exception145.

For example, desktop repair tool 125 may receive a first exception 145A.Desktop repair tool 125 may then search database 120 and determine thatexception 145A has occurred previously in system 100. Desktop repairtool 125 may also retrieve solutions 150 for exception 145A fromdatabase 120. In the illustrated example of FIG. 1, desktop repair tool125 retrieves first solution 150A and second solution 150B from database120. Each solution 150 may have been implemented previously to repairexception 145A. Desktop repair tool 125 may evaluate both solutions 150to determine which solution 150 to implement to repair exception 145A inthis instance. For example, database 120 may indicate the success rateof each solution 150 and provide a ranking of the solutions 150. Desktoprepair tool 125 may select the solution 150 with the higher and/orhighest ranking to implement. In the illustrated example of FIG. 1,desktop repair tool 125 may determine that solution 150B has a higherranking than solution 150A. In response, desktop repair tool 125 mayimplement solution 150B to repair exception 145A.

To implement solution 150B, desktop repair tool 125 may generate asoftware patch 155 that implements solution 150B. Desktop repair tool125 may then deploy patch 155 to a device 110 that threw exception 145A.That device 110 may then install patch 155 to repair a bug, error, orfailure that threw exception 145A. In this manner, desktop repair tool125 provides a resolution for a bug, error, or failure that has occurredpreviously in system 100 in particular embodiments.

Desktop repair tool 125 may detect a second exception 145B and determineby searching database 120 that exception 145B has not occurredpreviously in system 100. As a result, database 120 may not indicate anyresolution for exception 145B. Desktop repair tool 125 may then monitorthe device 110 that threw exception 145B as it is being repaired by alocal repair person. Desktop repair tool 125 may detect the steps 160that are performed to resolve exception 145B. If exception 145B issuccessfully repaired, desktop repair tool 125 may collect steps 160 andthen store them to database 120 for later use. If exception 145B occursagain in system 100, desktop repair tool 125 may retrieve steps 160 toprepare a second patch to repair the bug, error, or failure that threwexception 145B.

In particular embodiments, desktop repair tool 125 improves thefunctioning of devices 110 by repairing bugs, errors, and/or failuresthat occur in devices 110. In some embodiments, desktop repair toolcorrects bugs, errors, and/or failures that are not fixable by a localrepair person.

FIG. 2 illustrates a desktop repair tool 125 of the system 100 ofFIG. 1. As illustrated in FIG. 2, desktop repair tool 125 includes ascanner 205, a resolution engine 210, an alert engine 215, and a loggingengine 220. In particular embodiments, desktop repair tool 125 improvesthe functioning of devices in system 100 by resolving and/orimplementing solutions for bugs, errors, and/or failures that occur inthe devices.

Scanner 205 monitors various devices in system 100 to detect when thosedevices throw exceptions 145. In the illustrated example of FIG. 2,scanner 205 detects that one or more devices in the system 100 havethrown exceptions 145A and 145B. Exception 145A may be different fromexception 145B and may be caused by different bugs in different and/orthe same devices.

Scanner 205 may determine whether each exception 145 that it detects hasoccurred previously in the system. If the exception 145 has occurredpreviously in the system, then it is likely that the database has storeda resolution for the exception 145. Desktop repair tool 125 may use thestored resolution to repair this instance of the exception 145. Forexample, scanner 205 may query a database using keywords from eachexception 145 to determine whether the database has information on theexception 145. If the database has information about the exception 145,then scanner 205 may determine that the exception 145 has occurredpreviously in the system. For example, scanner 205 may determine thatexception 145A has occurred previously in the system, perhaps on anotherdevice. Scanner 205 may also determine that exception 145B has notoccurred previously in the system because the database does not includeany entry or any resolution for exception 145B. Scanner 205 may thenforward each exception 145 to resolution engine 210 with an indicationof whether the exception 145 has occurred previously in the system.

Resolution engine 210 determines and prepares resolutions for anexception 145. For exception 145A which has occurred previously in thesystem, resolution engine 210 may determine a resolution using previoussolutions 150. Resolution engine 210 may receive and/or retrievesolutions 150A and 150B for exception 145A. Each solution 150 may havebeen used previously to successfully repair exception 145A. For example,each solution 150 may repair a bug, error, and/or failure that threwexception 145A. Resolution engine 210 may select one of the solutions150 to implement.

Resolution engine 210 may select a solution 150 that has a higher rank225. In certain embodiments, a solution 150 may have a higher rank 225if it has a higher success rate of repairing a bug, error, or failurethat threw exception 145A than another solution 150. In the illustratedexample of FIG. 2, resolution engine 210 retrieves solutions 150A and150B for exception 145A. Solution 150A has a rank 225A and solution 150Bhas a rank 225B. Resolution engine 210 may compare rank 225A and rank225B to determine that solution 150B has a higher rank than solution150A. In certain embodiments, solution 150B may have a higher rank thansolution 150A because solution 150B has a higher success rate ofresolving the bug, error, or failure that threw exception 145A thansolution 150A. In response, resolution engine 210 selects solution 150B.This disclosure contemplates desktop repair tool 125 retrieving anynumber of solutions 150 for an exception 145 and determining thesolution 150 with the highest rank.

Resolution engine 210 generates a software patch 155 that implementssolution 150B. Resolution engine 210 may then deploy patch 155 to thedevice that threw exception 145A. The device may install patch 155 torepair the bug, error, or failure that threw exception 145A. In thismanner, resolution engine 210 repairs the bug, error, or failureautomatically without needing intervention by a local repair person.

For exception 145B, resolution engine 210 may determine that becauseexception 145B has not occurred previously in the system, that exception145B does not have a resolution stored in a database. As a result,resolution engine 210 must learn how to resolve exception 145B.Resolution engine 210 may monitor the device that threw exception 145Bto determine the steps that a local repair person followed to addressand/or resolve exception 145B. If the local repair person successfullyrepairs the bug, error, or failure that threw exception 145B, resolutionengine 210 may receive and record steps 160 that were followed by therepair person to repair the bug, error, or failure. Resolution engine210 may then store steps 160 in the database and associate it withexception 145B. Resolution engine 210 may then use steps 160 to preparea second software patch in the future that repairs the bug, error, orfailure that threw exception 145B should exception 145B be thrown againin the system. In this manner, resolution engine 210 repairs bugs,errors, or failures that repeatedly occur in the system.

In particular embodiments, resolution engine 210 also identifies andrecords a line of code that caused exception 145B. For example,resolution engine 210 may record an application in which exception 145Bwas thrown. Resolution engine 210 may also record a line of code in theapplication that was the source of the bug, error or failure that threwexception 145B. By recording the line of code, resolution engine 210 maybe able to subsequently prepare a patch to repair the bug, error orfailure.

In some embodiments, desktop repair tool 125 may determine that there isno solution for a certain exception. For example, scanner 205 may detecta third exception and resolution engine 210 may determine that there isno solution for the third exception. In response, resolution engine 210may record the third exception as an unsolvable exception.

In particular embodiments, resolution engine 210 may determine thatpatch 155 did not successfully repair the bug, error or failure thatthrew exception 145A. In response, resolution engine 210 may roll backthe deployment of patch 155 from the device. Resolution engine 210 maythen generate another patch that implements solution 150A and deploysthat patch to the device to repair the bug, error or failure that threwexception 145A.

In certain embodiments, desktop repair tool 125 includes an alert engine215. Alert engine 215 generates and communicates alerts 230. Alert 230may indicate an exception 145 and the particular resolution for thatexception 145. For example, alert 230 may indicate that exception 145Awas resolved by selecting solution 150B and deploying patch 155. Alertengine 215 may communicate alert 230 to an administrator to let theadministrator know that an exception 145 has been resolved and themanner in which it was resolved.

In particular embodiments, desktop repair tool 125 includes a loggingengine 220. Logging engine 220 may generate and maintain a log 240 thatindicates the various exceptions 145 and the resolutions for eachexception 145. For example, logging engine 220 may add an indicationinto log 240 that exception 145A was resolved by deploying patch 155.Logging engine 220 may also add an entry into log 240 that indicatesthat exception 145B was resolved by following steps 160.

FIG. 3 is a flowchart illustrating a method 300 for repairing desktopsusing the system 100 of FIG. 1. In particular embodiments, desktoprepair tool 125 performs method 300. By performing method 300, desktoprepair tool 125 improves the functioning of devices in the system byrepairing bugs, errors, and/or failures in those devices.

Desktop repair tool 125 begins by detecting first and second softwareexceptions in step 305. In step 310, desktop repair tool 125 determinesthat the first software exception had occurred previously and that thesecond software exception had not occurred previously in the system.Desktop repair tool 125 then determines first and second solutions forthe first software exception in step 315. In step 320, desktop repairtool 125 determines that the first solution has the higher ranking thanthe second solution. In step 325, desktop repair tool 125 generates asoftware patch that implements the first solution. Desktop repair tool125 then deploys the software patch in step 330. In step 335, desktoprepair tool 125 determines a series of steps implemented to resolve thesecond software exception. Desktop repair tool 125 then records theseries of steps to prepare a second software patch if the secondsoftware exception occurs again in step 340.

Modifications, additions, or omissions may be made to method 300depicted in FIG. 3. Method 300 may include more, fewer, or other steps.For example, steps may be performed in parallel or in any suitableorder. While discussed as desktop repair tool 125 (or componentsthereof) performing the steps, any suitable component of system 100,such as device(s) 110 for example, may perform one or more steps of themethod.

Although the present disclosure includes several embodiments, a myriadof changes, variations, alterations, transformations, and modificationsmay be suggested to one skilled in the art, and it is intended that thepresent disclosure encompass such changes, variations, alterations,transformations, and modifications as fall within the scope of theappended claims.

What is claimed is:
 1. An apparatus comprising: a scanner configured to:detect, in a desktop of a plurality of desktops, a first softwareexception occurring in an application of a plurality of executingapplications; detect, in a desktop of the plurality of desktops, asecond software exception occurring in an application of the pluralityof executing applications; determine that the first software exceptionoccurred previously in the plurality of desktops; and determine that thesecond software exception did not occur previously in the plurality ofdesktops; and a resolution engine configured to: determine a firstsolution and a second solution for resolving the first softwareexception; determine that the first solution has a higher ranking thanthe second solution; generate a software patch that implements the firstsolution in response to the determination that the first solution has ahigher ranking than the second solution; deploy the software patch;determine a series of steps implemented to resolve the second softwareexception; and record the series of steps to prepare a second softwarepatch if the second software exception occurs again in the plurality ofdesktops.
 2. The apparatus of claim 1, further comprising an alertengine configured to communicate an alert indicating that the firstsoftware exception can be resolved through the software patch.
 3. Theapparatus of claim 1, further comprising a logging engine configured to:add, to a log, an indication that the first software exception wasresolved using the software patch; and add, to the log, the series ofsteps that resolved the second software exception.
 4. The apparatus ofclaim 1, wherein the first solution has a higher ranking than the secondsolution because the first solution has a higher success rate ofresolving the first software exception than the second solution.
 5. Theapparatus of claim 1, wherein the resolution engine is furtherconfigured to identify and record a line of code that caused the secondsoftware exception.
 6. The apparatus of claim 1, wherein: the scanner isfurther configured to determine a third software exception occurring inan application of the plurality of executing applications; and theresolution engine is further configured to determine that there is nosolution for the third software exception.
 7. The apparatus of claim 1,wherein the resolution engine is further configured to: determine thatthe software patch did not fix the first software exception; and rollback the deployment of the software patch in response to thedetermination that the software patch did not fix the first softwareexception.
 8. A method comprising: detecting, in a desktop of aplurality of desktops, a first software exception occurring in anapplication of a plurality of executing applications; detecting, in adesktop of the plurality of desktops, a second software exceptionoccurring in an application of the plurality of executing applications;determining that the first software exception occurred previously in theplurality of desktops; determining that the second software exceptiondid not occur previously in the plurality of desktops; determining afirst solution and a second solution for resolving the first softwareexception; determining that the first solution has a higher ranking thanthe second solution; generating a software patch that implements thefirst solution in response to the determination that the first solutionhas a higher ranking than the second solution; deploying the softwarepatch; determining a series of steps implemented to resolve the secondsoftware exception; and recording the series of steps to prepare asecond software patch if the second software exception occurs again inthe plurality of desktops.
 9. The method of claim 8, further comprisingcommunicating an alert indicating that the first software exception canbe resolved through the software patch.
 10. The method of claim 8,further comprising: adding, to a log, an indication that the firstsoftware exception was resolved using the software patch; and adding, tothe log, the series of steps that resolved the second softwareexception.
 11. The method of claim 8, wherein the first solution has ahigher ranking than the second solution because the first solution has ahigher success rate of resolving the first software exception than thesecond solution.
 12. The method of claim 8, further comprisingidentifying and recording a line of code that caused the second softwareexception.
 13. The method of claim 8, further comprising: determining athird software exception occurring in an application of the plurality ofexecuting applications; and determining that there is no solution forthe third software exception.
 14. The method of claim 8, furthercomprising: determining that the software patch did not fix the firstsoftware exception; and rolling back the deployment of the softwarepatch in response to the determination that the software patch did notfix the first software exception.
 15. A system comprising: a pluralityof desktops; and a desktop repair tool configured to: detect, in adesktop of the plurality of desktops, a first software exceptionoccurring in an application of a plurality of executing applications;detect, in a desktop of the plurality of desktops, a second softwareexception occurring in an application of the plurality of executingapplications; determine that the first software exception occurredpreviously in the plurality of desktops; determine that the secondsoftware exception did not occur previously in the plurality ofdesktops; determine a first solution and a second solution for resolvingthe first software exception; determine that the first solution has ahigher ranking than the second solution; generate a software patch thatimplements the first solution in response to the determination that thefirst solution has a higher ranking than the second solution; deploy thesoftware patch; determine a series of steps implemented to resolve thesecond software exception; and record the series of steps to prepare asecond software patch if the second software exception occurs again inthe plurality of desktops.
 16. The system of claim 15, wherein thedesktop repair tool is further configured to communicate an alertindicating that the first software exception can be resolved through thesoftware patch.
 17. The system of claim 15, wherein the desktop repairtool is further configured to: add, to a log, an indication that thefirst software exception was resolved using the software patch; and add,to the log, the series of steps that resolved the second softwareexception.
 18. The system of claim 15, wherein the first solution has ahigher ranking than the second solution because the first solution has ahigher success rate of resolving the first software exception than thesecond solution.
 19. The system of claim 15, wherein the desktop repairtool is further configured to identify and record a line of code thatcaused the second software exception.
 20. The system of claim 15,wherein the desktop repair tool is further configured to: determine athird software exception occurring in an application of the plurality ofexecuting applications; and determine that there is no solution for thethird software exception.
 21. The system of claim 15, wherein thedesktop repair tool is further configured to: determine that thesoftware patch did not fix the first software exception; and roll backthe deployment of the software patch in response to the determinationthat the software patch did not fix the first software exception.